dashboard improvements and redisign #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also be a lot more verbose. This gives a better overview of what is still running and if it was restarted.
Case 1: Day matches and parent ID does not exist in artifact Case 2: Day matches (or 7 days into future) and parent ID matches any Stage 3 workflow
|
@yeoldegrove not sure if those are false or true positives, but I'm getting quite a few eslint errors in dashboardjs. Could you check if those are real? 
Also it is complaining about console.log (which is fine from my perspective but then we should configure eslint accordingly) |
|
This pr is too big to do a proper code review. Mostly looks good to me, and as the risk in this repo is very limited due to its scope, I'm fine with making an exception in this case to our 'no big PRs' rule. I do see quite a number of eslint errors when opening this in vs code, not sure if some of them might be false positives. @yeoldegrove I'm going to approve and leave the required lint fixes to your judgement |
fwilhe
approved these changes
Jun 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
The Garden Linux Daily Dashboard could be improved to give a better overview of our daily/nightly release workflows.
This adds:
Why is this needed:
The work in gardenlinux/gardenlinux#2711 e.g. splitted up the workflows so that the information to take into account to tell if a daily/nightly release was successful got more complex.
Currently there is no way to tell which workflows are related from the github UI or the dashboard.
gardenlinux/gardenlinux#2971 is another symptom of this.
Which issue(s) this PR fixes:
Fixes gardenlinux/gardenlinux#3085
Special notes for your reviewer:
The current development version is deployed via https://github.com/gardenlinux/daily-dev and available from:
https://silver-adventure-qromvjj.pages.github.io/
See README.md on how to configure a Github Personal Access Token.
additional changes to be done to https://github.com/gardenlinux/daily
mainbranch and only usegh-pagesbranchpackagesbranch which gets pushed to becronjob.shto get nightly packagessum up what the current next generation dashboard looks like
loading dashboard
pipeline in progress
pipeline in progress (including detailed information about parent workflow and historic releases)
historic successful release
historic successful release (parent workflow only possible since gardenlinux/gardenlinux#3100)
historic failed release